[QUIC] Remove check for AzL3 for QUIC and H/3 tests#126834
[QUIC] Remove check for AzL3 for QUIC and H/3 tests#126834ManickaP merged 1 commit intodotnet:mainfrom
Conversation
|
Tagging subscribers to this area: @karelz, @dotnet/ncl |
There was a problem hiding this comment.
Pull request overview
This PR removes the Azure Linux 3 VM-specific test gating that was added due to MsQuic failures, with the intent of re-enabling QUIC and HTTP/3 test execution now that SymCrypt images are expected to be updated.
Changes:
- Remove
IsNotAzureLinux3VMconditions from System.Net.Quic functional test classes. - Remove the
IsNotAzureLinux3VMcheck fromHttpClientHandlerTestBase.IsHttp3Supported. - Delete the
IsNotAzureLinux3VMhelper properties that implemented the AzL3 skip logic.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/libraries/System.Net.Quic/tests/FunctionalTests/QuicTestBase.cs | Removes the IsNotAzureLinux3VM helper used to skip AzL3 VMs. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/QuicStreamConnectedStreamConformanceTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/QuicListenerTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicRemoteExecutorTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicPlatformDetectionTests.cs | Attempts to remove AzL3 gating, but introduces an invalid ConditionalClass usage (see comment). |
| src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicCipherSuitesPolicyTests.cs | Drops AzL3 from the ConditionalClass gating list. |
| src/libraries/System.Net.Http/tests/FunctionalTests/HttpClientHandlerTestBase.SocketsHttpHandler.cs | Removes the AzL3 gating from HTTP/3 support detection and deletes the helper property. |
|
/azp list |
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This is still failing, the bare VMs have not been updated yet. I'm asking around in FR channel. I'll keep this opne for now, hopefully it won't take long to get updates in the images. |
|
that is curious. The images were rebuilt last week. I don't see Quic failures above. |
Because we don't normally run our tests on "naked" VM (sometimes we do, but I don't fully understand the heuristics), but outerloop does: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1380018&view=ms.vss-test-web.build-test-results-tab, and it's still failing: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-126834-merge-2f014b2698b447beb9/System.Net.Quic.Functional.Tests/3/console.8b9de10c.log?helixlogtype=result And FR are on it, we figured out that it should be rebuilt and packages updated, but somehow they aren't... So it's being investigated. |
|
/azp run runtime-libraries-coreclr outerloop |
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
It's running now: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-126834-merge-25aff52c34004111b1/System.Net.Quic.Functional.Tests/1/console.d4105419.log?helixlogtype=result |
|
/ba-g unrelated |
Fixes #123216
SymCrypt 1.9.5 is out, docker images are already fixed, let's see if the base VM images are up-to-date or need re-building.